Rejection Codes
The payer's payment service provider can communicate the reason for rejecting a given transaction to the Aggregator using the codes listed in the following table. The first block of the table contains the partner bank and GIROInstant error reasons received in the final status report (FSR). The second block contains error codes specific to purchases executed via the schema. The third block contains a single catch-all error reason code, which is used for all other rejection cases not listed previously. This includes sensitive rejection reasons that cannot be displayed to third parties.
| Code | Business case | Rejecting party | From FSR only | From pre-execution check only |
|---|---|---|---|---|
| AB05 | Timeout at beneficiary bank | GIRO | x | |
| AB06 | Timeout at payer's bank | GIRO | x | |
| AB07 | System participant currently unavailable | Beneficiary bank | x | |
| AG01 | Transaction type not permitted for the given account type | Either bank | ||
| AM06 | Transaction amount lower than the minimum established for the given account | Either bank | ||
| AM05 | Duplicate message | Payer's bank | x | |
| NOOR | For investigation message: original mandate not found | GIRO | x | |
| Schema-specific error codes | ||||
| DS0D | Signing certificate revoked, does not pass verification | Payer's bank | x | |
| DS17 | Authentication code of the unified data carrier solution is incorrect (signature error) | Payer's bank | x | |
| DS0E | Certificate unavailable | Payer's bank | x | |
| Catch-all error code | ||||
| MS03 | Unspecified reason for refusal | Any party |